The Datafile PD-CD 1 Issue 2/PDCD-1 - Issue 02.iso/_comms/comms/_fidomail/!FidoMail_Resources_FidoMail_HelpData

Text File | 1994-02-19 | 38.4 KB | 1,013 lines

Help on FidoMail
#sprite 0,0 !fidomail
#indent 5
       FidoMail 1.86 (19 Feb 1994)
       ---------------------------
#indent 0

This help system divides the helpful texts into small
windows, which can be opened from each other by a
click on the <red words=>red_words>.

An appropriate help page will be opened if you place
the pointer over an icon in FidoMail, and press F1.

The help system is written by Guttorm 'ArmStrong' Vik
FidoMail is written by Thomas Olsson


                    Main pages
                    ----------
                < Getting started!  =>getstarted>
                <  Using FidoMail   =>using_fm>
                <An automated system=>sorry>
                <     Problems      =>sorry>Address
Your address is your way of identifying yourself to
other systems.

Your address is build up from 4 components:
Zone:Net/Node.Point. E.g.: 2:252/102.40
(This is often called a 4D address, because of the
 4 numbers)
The Zone (2) is a large area, 2 is Europe/Asia.
The Net (252) is a smaller area in a zone, 250-259
 is Britain.
The Node (102) is a single system in a net, 102 is
 The World of Cryton.
The Point (40) is allocated locally at the Node to
 identify a sub-system, such as yours.
You must always give people your address, if they
are to be able to write mail to you.
Sometimes, you will encounter a 5D address, which
is your 4D address with a 'domain' name attached to
the start or the end. In fidonet, it will look like
either of these:
2:252/[e-mail]
FidoNet#2:252/102.40No letter
Oh. Something must be wrong then. If you've checked your
setup twice already, there's the faint, tiny, small
possibility, that your boss has done something wrong in
his setup. Ask him politely to check it.
He will also be able to examine the packet you sent, and
he may find some clue in that. Meanwhile <check=>setupex> your
setup again, especially the <addresses=>address>. One single typing
error can make it all fall over.Area identifiers
The area identifiers are global words which
identify the areas. Your <boss> will know which
areas he has available, and the identifiers.
E.g. The international Archimedes area has
the identifier 'ARCHIMEDES'Binkley won't dial
Check your Mailer configuration (especially the
'Init' string - consult your modem manual). If
Binkley writes 'Couldn't find Zone/Net/Node...'
check the address given.
If it's ok, you've got a faulty nodelist, call
your boss and complain.Setting up the mailer
Configuring the mailer is beyond the scope
of this help info. Refer to the manual for
Binkley or Netway.Boss
Your Boss (or uplink) is the system you
are going to get your mail from. If you
are a point, you will usually only have
one boss.
Locate the nearest fido-BBS and ask the
SysOp to give you a point number under
his system.Essentials
To run a point system you will need:
A modem
FidoMail
A <Mailer>
An <archiver>
An <ARCmail> packer

It's possible (in theory) to run a
point on floppy, but a harddisk is
definitely recommended!FidoMail Config file
You will need to replace the addresses etc. with the ones
for your system:

Spark     - The <location=>putapps> of your <!Spark=>archiver>, if you have one.
SparkMail - The command given to run <!SparkMail=>arcmail>
Origin    - An origin line of your choice (max 63 chars)
RouteMap  - The way to <route=>routemap> mail that go through your system.
            Usually you will just need to replace the address
            with your own.

You shouldn't need to worry about the rest of the file for now.
If you want more information about it, click <here=>*Filer_Run \<FidoMail$Dir\>.Dox.Config>.
Next file to edit is the config file for the Fidonet domain.
Click <here=>*Filer_Run \<FidoMail$Dir\>.Domains.FidoNet.DomainCfg> and then <here=>fmconfigdom>.FidoMail setup
If you've done the mailer setup, this will be a
piece of cake.

Open the Config directory by clicking <here=>*Filer_OpenDir \<FidoMail$Dir\>.Config>.
Edit the <Main=>*Filer_Run \<FidoMail$Dir\>.Config.Main> file, and click <here=>fmconfig> to continue.Getting started
First, let me give you a hint about this <help system=>helphint>.
Setting up a proper fidomail system requires quite a few programs,
so make sure you've got <all of them=>essentials>.
Furthermore, you'll need to make arrangements with your <boss>, who
should prepare his system for you. At regular times, you (or your
computer) will be <polling> his system, and for this purpose, he
will allocate a suitable time for you. Also, you will get a
<point number=>pointno> or a <node number=>nodeno>. You should, in turn, tell him about
which conferences (areas) you wish to receive. When all these
preparations are completed, you must tell all the various programs
about the characteristics of your system. This is a difficult task
without guidelines, so when you know <all the numbers=>neednos>, look at the
<setup example=>setupex>.

When everything appears to be ready, <try it out=>systest>, but make sure
your boss is home, he will be able to help.Succes!
Congratulations, most of your setup is certainly working
like it should. If you'd like to write <echomail> at some
stage, you will also need to set up your <AreaMap>.
The real test of your system  is of course daily usage,
where all kinds of strange things may happen. But for
now, feel free to explore the features of Binkley,
<FidoMail=>using_fm> and the international fido network.Help Hint
When FidoMail is running, you will be able to browse through
these pages. When FidoMail dies, the help page is closed.
If you want the FidoMail help pages available at all times,
do this:

Click <here=>*Filer_OpenDir \<StrongHelp$Dir\>.HelpData> to open the StrongHelp data directory.
Click <here=>*Filer_OpenDir \<FidoMail$Dir\>.Resources> to access the FidoMail help data.
Copy the 'FidoMail' directory into the 'HelpData' directory.
Restart StrongHelp.

Now you will always be able to get help on FidoMail by
choosing its item from StrongHelp's iconbar menu.Your name
Just your name... You do
have a name, don't you? :-)Area line
This line shows which area this message belongs
to. You can change area by clicking the ê Area ë
icons, or by pressing Shift + Left/Right arrows.
You cannot go to an area with no <valid=>validmsg> messages
in it.Previous Area
This icon will move to the last <valid=>validmsg>
message in the previous area. Pressing
Shift-left has the same effect.Next Area
This icon will move to the first <valid=>validmsg>
message of the next area. Pressing
Shift-right has the same effect.Date line
This line shows the date at which the message
was last altered (by the sender), which is
usually the date it left his system. This line
is used by FidoMail when doing a <weed> where
the 'age' is significant.From line
This line shows the name of the person who wrote
the message. (Also termed 'the sender')
Clicking on 'From:' will allow you to put the
sender into the <address book=>addrbook>, or to edit the
entry, if he's already in there.Private Reply
Clicking this icon will open the
<Outgoing window=>outwind>, prepared for a
<netmail> reply from you to the
sender of the message.Subject line
This line is (usually) a short description of
what the message is about.To line
This line shows who the message is for.
(Also termed 'the receiver')Message properties
Each message has got a number of
attributes. First of all, it resides
in a certain area.
Furthermore:
It may be a <CrashMail=>crash>
It may be <Read> (by you)
It may be <New>
It may be <Sent>
It may be <Personal>
It may be <Marked>
It may be <Found>Mailers
The 'mailer' is the program that actually uses the modem to
call other systems and exchange mail. There are currently
two suitable mailers for the Archimedes.

Binkley (ported by Geoff Riley, Hugo Fiennes, Steven Haslam
and Keith Hall) can be downloaded from most BBS's. You will
need version 2.09h or greater.

NetWay (by Steven Haslam) is shareware, and you are urged to
register it if you want to keep on using it in your system.Things needed
When your <boss> has prepared his system, you will need to have
these:

Your <address>, e.g. 2:252/102.40
The <identifiers=>areaident> of the areas you wish to receive.

Also, you need a Nodelist, containing at least your boss,
usually called 'NList_xxx'. If you haven't got ParseList (by
Hugo Fiennes again), get it, or try to persuade your boss to
compile the nodelist for you. You can also use !NListMgr by
Steven Haslam. You will end up with a compiled nodelist, which
your <mailer> will want.ARCmail packer
SparkMail is an ARCmail packer,
written by Hugo Fiennes. It will control
Spark, and arc the mail that you are going
to send. If you are a point, you will only
ever send the mail you write yourself, so
it is not vitally important to arc it. If
you don't have <Spark=>archiver>, you won't have any
use for SparkMail either. It is PD, and
can be downloaded from most BBS's.
You will need version 1.10 or greater.Archiver
Spark is a brilliant archiver by David Pilling.
It is used to unarc the packets you receive, and to arc
the packets you will send. It is not free, but the price
is very reasonable. If you don't have Spark, you can use
SparkPlug, which will only unarc. This also means that
you won't need SparkMail.

Spark can be purchased from:
David Pilling
P.O. Box 22,
Thornton Cleveleys,
Blackpool.
FY5 1LR.
United Kingdom.Point Number
Your point number is allocated by your <boss>,
and will be used by both your and his system
to identify the mail to or from you.
The point number is the last number in your
<address>.Polling
Polling is the done by your <mailer>, when it is
dialing up your <boss>, to send your outgoing mail
(and files), and receive any incoming mail (or
files).
The task can be performed either at a scheduled
time, or when you ask for it.Where to put things
You probably already have a Comms directory or
disc. Put !Binkley and !FidoMail into that.
Put !Spark and !SparkMail into your Library,
or any other directory which is included in
your \<Run$Path>. If you don't have a Library,
create one.Reading mail
When you wish to read some mail, click
on a <group> in the <Summary window=>sumwind>. This
will open the <Incoming window=>sorry>.
If you use Adjust, you will instead get
a <list=>grouplist> of the messages in the group.Red Words
The red words in the help text is a way of
getting additional information quickly.
When a sentence contains such a word, you
can open another help page by clicking on
it, which will give further details about
the word in question.

The words work like filer directories, so if
you use adjust, the previous page will be
closed. Adjust on the close icon will open
the previous page.Setup example
Your system can be set up in a variety of ways, but if
you're new to points, it will be a good idea to build
it up using this example.

 1. Make sure you've got all <the programs=>essentials> and all
    <the info=>neednos> you need.
 2. Move the applications to into <handy directories=>putapps>.
 3. <Setup the mailer=>mailersetup>.
 4. <Setup FidoMail=>fmsetup>.To be continued...
Sorry, this part of the
help system has not yet
been written.Summary window
The Summary window is opened by clicking on the FidoMail
icon, or by closing the Incoming window with Adjust.
Most reading and writing of mail is initiated from this
window. It will display a vertical list of areas, and a
horizontal line of <message-attributes=>msgattr>. Below them is an
array of numbers, which is the number of messages in the
area with those attributes (called a '<group>').
You will be able to click on a group (if it contains any
messages at all), which will display the first message in
that group. If you use Adjust, you will get a <list=>grouplist> of the
messages in that group.
You can also click on an area name, which will open the
<Outgoing window=>outwind>, enabling you to write a message in that
area.
Clicking Menu in the summary window produces a <menu=>sorry>, the
contents of which depends on where you pressed menu.
The topright corner displays which AKA you are currently using,
and thus the name related to <personal> messages.Testing the system
First, check that all applications are able to start up at all.
!SparkMail needs some parametres, so try it, and you should get a
'Usage: ...' message.
Try !Spark. If it won't start (very unlikely) consult the manual.
!FidoMail is already running, so if you've made any mistakes you should
have been told.
Now try !Binkley. You may get a brief flash of an error message and it
dies. This is quite normal, and almost certainly due to a typing error
in one of the files, so check them.
When it starts properly, click on the icon and check the info in the top
window. You don't have to check which OS you have running, but look at
the top left corner, it should display your <address>
(e.g. 2:252/[e-mail]).
Now call your boss voice, and say that you're going to poll him in a
minute. Make him watch the progress at his end.
Bring the Binkley menu up, and move to 'Commands=>Manual poll=>...' and
type the <Net/Node=>address> of your boss, e.g. 252/102
After a few seconds, Binkley should call your boss.
If this doesn't happen, click here: <"It doesn't happen"=>binkerr1>
Now a lot of activity should begin, hopefully ending with an 'End of
WaZOO session'.
If your HUB had some mail waiting for you ('on hold'), you will see
further action.
If he hadn't, call him, make him write a <netmail> for you, and try again.
Now you should see 'Exit after receiving mail with errorlevel 5' (or 6).
What should happen next is that FidoMail starts and examines the mail
('tosses' it). This requires that you have told Binkley what to do after
receiving mail. This is done in the 'errorlevel' files, and again you
should consult the manual for the mailer.
Click to <continue the testing=>systest2>Further testing
When you have started FidoMail, examine the Inbound directory. This is
usually located inside Binkley, or in !Net_Areas. It should contain a
file called 00000028M1 or xxxxxxxxPT or something similar. If it is an
archive, select 'Unarc' in FidoMail, or click <here=>*\<FidoMail$Dir\> -unarc>.
Now Spark(Plug) will have been started, and your mail should have been
unarc'ed, otherwise you may have made a mistake in the Spark entry in the
<Main-config=>fmsetup> file.
When this is completed, or if your mail wasn't arc'ed, select 'Toss' in
FidoMail, or click <here=>*\<FidoMail$Dir\> -toss>.
You might get a window saying 'That packet is for xx:xx/xx.xx'. If that
happens, it means that either you or your boss has made a mistake
concerning your address. Check with your boss and in your configuration.
Otherwise FidoMail will have tossed your mail into the appropriate areas.
Click Select on the FidoMail icon. This will open the Summary window.
You should see 1 new message, click Select on the '1'.
This will display the message from your boss.
Call your boss and tell him.
You will be able to reply to his message by clicking the Pr.Reply button,
do that. Now write your reply, and click Save when you're finished. Disc
activity, and the window closes. Now for the last test:
Will he get the message?
Choose 'Scan' from the iconbar menu, or click <here=>*\<FidoMail$Dir\> -scan>.
Start Binkley and click the Binkley icon. The 'Pending Outbound' should
have gotten a line, stating your boss's <address=>address> and some stars and
things. Do the manual poll again.
Binkley dials, does a lot of things, and hangs up. Call your boss and ask
him if he just got a letter.
Had he? <"Yes"=>gotit> <"No"=>aintgotit>Using FidoMail
FidoMail is used for some general purposes:

                <Reading mail=>readmail>
                <Writing mail=>writemail>
              <Requesting files=>sorry>
               <Sending files=>sorry>

After a while, you might wish to use some of
the:

             <Special functions=>sorry>
           <Maintenance functions=>sorry>Writing mail
When you wish to write a letter, click
on an area in the <Summary window=>sumwind>. This
will open the <Outgoing window=>sorry>.Node Number
Your node number is allocated by your NC, and
will be included in the worldwide nodelist,
as well as in the local ones in your area.
To get a node number, you must have a working
system, and it must be available for mail in
ZMH (0230-0330 GMT). When using a 4D <address>,
you will appear as point 0.Domain configuration
The things to alter in this file are:

AKA     - Your <address> in 4D format, and your <name=>hisname>.
SetArea - This is a list of the areas you wish to receive,
          and their <identifiers=>areaident>. You can choose the text
          in the quotes as you like, but the uppercase
          identifiers must be exact.AreaMap window
The area map window governs which <downlinks> you have, and what areas they get.
There is a column of buttons for each downlink, and a line for each area.
If a button is pressed, it means that the downlink will get the messages in
that area, when the mail is <scanned=>scanning>.
A downlink can 'click' the buttons himself by writing a message to <AreaFix>.
You can prevent him from connecting or disconnecting himself to an area, by
'locking' it.
When you press menu, you will be able to edit some things about the downlink.
The 'Name tag' is only used as a headline for each downlink.
The 'Address' is the <address> of the downlink.
The 'Flags' are currently only 'Hold' which sets whether the packet should be
sent or put on <hold>.
'Copy' will make a copy of the downlink info.
'Delete' will remove that downlink.
To make a new downlink, copy an already existing one, and edit that.

When you are editing the map, the changes will have immediate effect, but if
you want them to stay permanent, click Save.

In a simple point system, you will usually only have 1 downlink, and that is
your <boss>. So, if you are 1:234/567.8 you should have a downlink called
1:234/567, with all the areas active. If some of them are not, the mail you
write in that area will go no further that into the messagebase. This can be
used if you are connected to any <read-only> areas.Downlinks
Downlinks are systems that get <echomail> from
you.
In fido terms, it usually only means systems
'below' you in the net structure, and the ones
you get mail from is called uplinks.
In FidoMail, however, downlinks are everybody
you exchange mail with, no matter where they
are in relation to you. There is no technical
difference between uplinks and downlinks.Scanning
Scanning is the proces of checking through
the message base, and making mailpackets for
your <downlinks>, which you have defined in
the <AreaMap>.
For <echomail>, FidoMail uses the SEEN-BY
information in a message to determine which
downlinks hasn't yet seen that message. They
will then get it if they are connected to
the area.
<Netmail> is scanned in a completely different
way, according to the <routemap>.AreaFix
The AreaFix processor provides your <downlinks> with means
of controlling which areas they get when you <scan=>scanning>.
This is done by sending a <netmail> from their system to
AreaFix.
The message should contain lines with commands of the
following types:

-\<area> will disconnect the downlink from that area.
+\<area> will similarily connect it.
?       will return a help text, and a list of currently
        connected areas.

\<area> is the <area identifier=>areaident> of the area.
The AreaFix processor will always generate a reply to the
request, listing the registered changes.
The locks in the AreaMap window will prevent the downlink
from changing his connection status on this area.Hold
When a packet is 'on hold' for
somebody, it means that the
packet will not be sent, unless
the 'somebody' calls to get it.Read only
An area can be marked as read-only by
appending 'ReadOnly' to the appropriate
SetArea line. You will not be able to
write messages in such areas.
You can also deselect your boss from
the area, using the <areamap> window,
which will ensure that nothing in that
area gets any further than into your
messagebase. This will ensure that any
points you have won't be able to write
<echomail> in that area by accident.Routemap
The routemap defines how you want <netmail> to travel.
It is usually defined in the Main config file, as 'RouteMap' commands.
These are of the form: RouteMap \<dest_addr\> \<scan_addr\> [H]
For example, if you write a netmail to Australia, you wouldn't want
your computer to actually call Australia and deliver the mail (unless
you actually live there of course). Instead, you send the mail to your
boss, who then in turn sends it to his boss and so on... until the
mail arrives at it's destination. The way to do that is to set up
different routes for different destinations. To define that example,
if your boss is called 2:252/102.0:

RouteMap 3:*/*.* 2:252/102.0

So everything aimed at zone 3 (where Austalia is) will instead go to
252/102. The '*' means any number. Now, if you live in zone 2, you
wouldn't want to write the above line for each possible zone, so
there's an easier way. The RouteMap lines are checked from the top
until FidoMail meets a line that covers the destination address. So,
for example, to make everything to zone 2 go direct, and everything
else via 252/102, you would write:

RouteMap 2:*/*.* 2:*/*.*
RouteMap *:*/*.* 2:252/102.0

Note that the stars in the \<scan_addr\> means that the real destination
numbers will be used there. You should always have a '*:*/*.*' at the
end of your RouteMap list, to ensure that there is always somewhere to
send netmails. If you haven't got that, and a netmail comes in with a
destination which can't be found in the route map, it will be put on
<hold> for that destination, so your system will not begin calling
anywhere unpleasant. (This is equivalent to a 'RouteMap *:*/*.*
*:*/*.* H' at the end of the list)

Let's take a final example. You may need to send all national netmails
to your boss, all international mail to another node, and if you have
any points, you would want to put everything to those on hold for them
to pick it up.
So, if you are called 2:252/256.0, your boss is 2:252/102.0, and the
international node is 2:254/27.0, you would write:

RouteMap 2:252/456.* 2:252/456.* H
RouteMap 2:25?/*.*   2:252/102.0
RouteMap *:*/*.*     2:254/27.0

There are some unknown things here: Appending an 'H' to the line means
'put the packet on <hold>'. '?' means 'any digit', so 25? matches the
numbers from 250 to 259.

Finally, if the netmail has <crash> status, the routing is disabled.Valid messages
A message is said to be 'valid', if
it is included in the <group> you are
currently reading.
If, for example, you are reading all
'New' messages, the old messages will
be invalid, and the new ones will be
valid.Crashmail
'Crash' status is something that can
be applied to <netmails=>netmail>. It means that
the mail will be sent directly to the
destination, rather than being <routed=>routemap>
the usual way.Netmail
Netmail (as opposed to <echomail>)
is  simply another word for
'private mail'. Writing a netmail
differs from writing an echomail
in that it needs a destination
address, because only one person
will receive it.Echomail
Echomail (as opposed to <netmail> is
a term used for 'public messages'.
It is written in an area (or 'echo'),
and everybody who reads that area
will receive the message.Group
A 'group' of messages is any number of
messages which are somehow related. For
example, 'All new messages', or indeed
'All messages'.
Messages can be treated according to
the group they are in, for example, you
can <read messages=>readmail> in a certain group,
or <save a group=>savegroup> etc.List of group
Clicking Adjust on a group in the
summary window will display a list
of the messages in that <group>.
Unread messages will be listed in
red. You can click on a line in
the list to read that group,
starting at that message.Save a group
It is possible to save a group of messages
using the Summary window.
If you press Menu over a group (an icon with
a non-0 number), the Save entry will enable
you to save all the messages in that group as
a text file.

The messages will be separated by a few lines,
stating the sender, receiver and subject.
These lines can be <changed=>grouphdr> to suit
your needs.The GroupHdr file
In the Misc directory of each domain, there is a
file called 'GroupHdr'. This file contains the
textlines to put between the saved messages. Like
<footers=>expstrings>, they can contain special characters to
extract information from the actual message.

This process is controlled by putting %-variables
in the lines. A %-variable consists of a % and a
letter, which then will be replaced by some part of
the message.
Currently recognised fields are:

Field:    Replaced by:
--------------------------------------------------
%t        To (The receiver of the message)
%t1       To (first name)
%t2       To (surname)
%f        From (The sender of the message)
%f1       From (first name)
%f2       From (surname)
%s        The subject of the message
%d        The date of the message
%c        The time of the message
%a        The area where the message belongs
%i        The area-identifier of the area in which
          the message belongs.
%%        %

There is another field which is only meaningful in
the '<Forward=>forwardfmt>' file. This is '%text', and will cause
the text body of the forwarded message to be
inserted.Expanded strings
About the expanded strings: Footer, Quote, TearLine &
Origin.
These are defined in the Config file, in one of 4 ways:

<Type 1=>expstr1>: "" or not defined at all
<Type 2=>expstr2>: "\<string>"
<Type 3=>expstr3>: "%File:\<filename>"
<Type 4=>expstr4>: "%List:\<filename>"

When a normal string is remaining, it will be expanded.
This process is controlled by putting <%-variables=>expstrvar> in
the string.Examples of expanded strings
Generating a random footer from a file of footers.
--------------------------------------------------

Make sure the footer-file contain single-line footers
(not too long) separated by LF (!). Put the file in
a 'Misc' directory inside !FidoMail for convenience.
Let's say it is called 'Footers'. In the !Config file,
you would write:

Footer "%File:\<FidoMail$Dir>.Misc.Footers"


Generating a different Origin line for each area.
-------------------------------------------------

If, for example, you have 7 areas speaking different
languages, you could make a file like this:

\<NET>:
ARCHIMEDES:Point Blank
ARCCOMMS:A Pointless Point
ARCPROG:Point of No Return
ZAKE:Beze mel yrk Point krutzfer heno
TEUSCH:Point "Boom Thscak"
UMBA:Hrunga okosa Urapun

Put it in the Misc directory as before, named 'Origins'
Then, in the !Config file, write:

Origin "%List:\<FidoMail$Dir>.Misc.Origins"

The first area, which is netmail, would have no string,
as there's no * Origin line on netmails. Each of the
other 6 areas will have their own origin line.


Generating random footers in several languages.
-----------------------------------------------

This is done as a combination of the above.
If, for example, you have 2 footer-files,
imaginatively called 'FootersUK' and 'FootersDK',
containing footer-lines in English and Danish.
First, the !Config file should read:

Footer "%List:\<FidoMail$Dir>.Misc.FooterPtr"

The 'FooterPtr' file should consist of 1 line per area:

\<NET>:=== My Point - Mit Point ===
ARCHIMEDES:%File:\<FidoMail$Dir>.Misc.FootersUK
ARCCOMMS:%File:\<FidoMail$Dir>.Misc.FootersUK
ARCPROG:%File:\<FidoMail$Dir>.Misc.FootersUK
LOKALA:%File:\<FidoMail$Dir>.Misc.FootersDK
LOKALQ:%File:\<FidoMail$Dir>.Misc.FootersDK

The first line is in both languages for netmails, but
could simply be empty to get no footers on netmails.
The next 3 areas have English footers, and the last 2
have Danish ones. Any other areas will have no footer,
since there is no '\<ALL>:' line.


Interresting quoting.
---------------------

You could have a selection of Quote-headers in a file
and select one at random. The file could contain:

Quoting %q:
Well, %q, %d you said:
I suddenly saw %q writing:
%q said this about '%s':
Allow me to quote %q:
... and so on.

So, as you see, the % fields will be replaced by the
relevant data as described above. You can combine this
with the previous example to get both quote-headers
and footers in different languages (or to suit
different moderators :-).Redirection Type 1
This will not insert anything in your messages, not
even empty lines. To get empty lines, use " " (a
space). The Origin text must not be empty, so a text
is mandatory. The TearLine text can be empty (giving
only '--- '), but if it is undefined, it will revert
to 'FidoMail v.\<version> (\<date>)'.Redirection Type 2
This will insert the given string into your messages,
after expanding it according to the <rules=>expstrvar>.Redirection Type 3
This command causes redirection to the named
file. A random line is read from the file,
and then processed as a new command, which
may be of types 1-4.Type 4:
Another type of redirection. This is like <type 3=>expstr3>,
but it is not a random line. Instead, the line read
will depend on the area you are writing the message
to.
Each line should start with '\<area>:', e.g.
'ARCHIMEDES:%File:\<FidoMail$Dir>.ArcFooters'
This will take a random line from that file when
writing messages in the Archimedes area.
Special areas are '\<NET>', '\<JUNK>', and '\<ALL>'.
If '\<ALL>' is met before the area could be found,
that line will be used.Expanded fields
A %-variable consists of a % and one or more letters,
which will then be replaced by some part of the
message. Click here for some <examples=>expstreg>.
Currently recognised fields are:

Field:  Replaced by:
%t      To (The receiver of the message)
%t1     To (first name)
%t2     To (surname)
%s      The subject of the message
%d      The date of the message (the original, if
        writing a reply)
%c      The time of the message (otherwise as %d)
%q      The person you are quoting (usually the same
        as %t)
%q1     The person you are quoting (first name)
%q2     The person you are quoting (surname)
%a      Quote header: The area in which the quoted
        message belongs.
        Footer: The area in which your new message is.
%i      Same as %a except this is the actual fido-
        identifier for the area.
%%      %Forward format
Like the <GroupHdr>, there is a file
called 'Forward'. This file has the
same format, and is used to define
how a message will look when you
forward it to somebody.Read messages
A message is said to be 'read'
when is has been displayed, and
you have moved on to the next
message or closed the window.
A message will not be 'read' if
you 'goto' another message, or
browse through the messages by
clicking in the <list=>grouplist> window.New messages
When messages are <tossed=>tossing>, the
existing ones are marked as 'old',
and the recently tossed ones are
'new'. They will then remain new
until the next toss.
The exeption from this is, if the
messages are tossed using the
'-tosson' CLI-option. The existing
'new' messages will then remain new.
You can explicitly make all messages
'old' by using the '-resetnew' CLI-
option.Tossing
Tossing is the process of reading
any mailpackets from the inbound
directory, and putting them into
the messagebase at the right
positions.
Tossing is started by selecting
'In ëToss' from the iconbar menu,
or by using the '-tosson' or
'-toss' CLI-options.Sent messages
When a message is 'Sent', it
means that FidoMail has checked
whether anybody else should have
this message, and, if that was
the case, made a packet for them.Personal messages
Personal messages are messages
that are either to or from you.
'You' in this case means the
current sysopname, which can
be changed using the <summary=>sumwind>
window.Marked messages
Marking a message has no fixed
meaning in FidoMail. It is meant
as a 'user-flag', the meaning of
which you define yourself. The
default meaning of this flag is,
that marked messages will not be
killed by most <weedtypes>.
It should be emphasized that this
behaviour is just an example, and
you can use the 'marked' flag for
completely different things.Weedtypes
The Weedtypes are listed in the
'Misc ë Weed' menu, and are used
to kill messages of certain
types or ages.
They are fully <user-definable=>weeddef> by
editing the config file.Found messages
'Found' messages are messages
that were found by the last
<search> operation.Search
......
Defining your own weeding types
By default, it is possible to define up to
16 weed types.
This is done in the !Config file with the
'WeedType' keyword.
For each weedtype, write a line like this:

WeedType \<name> [\<clause>[ \<clause>...]]

The \<name> will appear in the 'Weed' menu
and should be 1-12 letters. The \<clause>
(if present) is one or more <booleans=>weedbools>.
(Case doesn't matter)

To determine whether a message should be
deleted, the booleans are calculated, and
if ALL OF THEM are true (ie there's AND
in between), the message is deleted.
Missing booleans are 'Don't care' (not
checked). <Examples=>weedeg>.WeedType booleans
<Found>
<Read>
<Sent>
<Personal>
<Marked>
<New>

The booleans can also be prefixed
by Not (eg. 'NotSent') which will
negate their meanings.
Furthermore, there is:

Age\>xx
Age\<xx

which will be true if the message
is in the range specified.WeedType examples
An example would be 'Delete all mail which is
older than 14 days, but not if I haven't <read>
it or it haven't been <sent> yet or if I've
<marked> it as important.'
This is expressed in the !Config file as:

WeedType "Fortnight" Age/>14 Read Sent NotMarked

Which, in words, could be expressed as:
'Delete messages whose age is greater that 14
days AND which is read AND sent AND not marked.'

Another example:
'Delete all mail except the important (<marked>)
mail and my <personal> mail.'

WeedType "Clean" NotMarked NotPersonal

One more:
'Retain only the <latest=>new> messages and the <marked>
ones'

WeedType "Old" NotNew NotMarked

Yet another example:
'Delete all mail'

WeedType "All"

(there's nothing after the name, so everything
is 'Don't care')Group line
This line shows a description of the
<group> you are currently reading.
You can change group using the locks
to the right, or by selecting another
group from the <summary window.=>sumwind>Message number
This icon shows the current message
number, and the number of messages in
the current <group>.
The message number is not a fixed
quantity, and depends entirely on the
group. For example, the same message
could be number '3 of 10' when reading
'All personal mail', but number
'45 of 210' when reading 'All new mail'.

Clicking on this icon produces a <list=>grouplist>
of the contents of the current group.Address book
.....Weeding
....Delay line
This line displays the delay, from the
moment the message was last edited by the
sender, to the moment it was received by
FidoMail on your system.
In your own messages, this will be 'None'Outgoing window
.....Reply
Clicking this icon will open the
<Outgoing window=>outwind>, prepared for a
<echomail> reply from you to the
sender of the message.
If the area is a filelist-area,
this button will instead allow
you to <filerequest=>freq> from the
system that sent the message.File requesting
....Edit message
This button will allow you to edit the current
message.
If the message is not from you, or if it has
already been sent, the button will be inactive.
You can make it active anyway by turning 'Edit
all' on in the menu, but note that this will
enable you to annoy many other people if you
don't know what you are doing.Thread button
This button will open the <Thread window=>thread>
If the current message has no message-id,
it cannot belong to a thread, so this
button is sometimes inactive.Thread window
.....Move backwards
This icon will move to the
previous <valid=>validmsg> message.
Pressing the left-arrow
has the same effect.Move forwards
This icon will move to the
next <valid=>validmsg> message.
Pressing the right-arrow
has the same effect.'Read' status
This icon displays whether the
message has been <read> or not.
Clicking the icon will toggle
the status.
This may have <side effects=>sfx>.Side effects
Toggling any of the attribute-buttons
in the incoming window may have
surprising side effects. These can be
useful in some cases, when you know
what is going on.
If toggling the button means that the
message becomes <invalid=>validmsg>, the next
valid message will be displayed
instead. If there are none of these,
the previous valid message will be
displayed. If there no valid messages
left, the window will close.

You can see at a glance whether the
abovementioned situation will happen.
If the lock is 'locked' beside the
attribute you are about to toggle,
the message will become invalid.'Scanned' status
This icon displays whether the
message has been <sent> or not.
Clicking the icon will toggle
the status.
This may have <side effects=>sfx>.'New' status
This icon displays whether the
message is <new> or not.
Clicking the icon will toggle
the status.
This may have <side effects=>sfx>.'Personal' status
This icon displays whether the
message is <personal> or not.
Clicking the icon will toggle
the status.
This may have <side effects=>sfx>.'Marked' status
This icon displays whether the
message is <marked> or not.
Clicking the icon will toggle
the status.
This may have <side effects=>sfx>.'Crash' status
This icon displays whether the
message is a <crashmail=>crash> or not.
Clicking the icon will toggle
the status.
This may have <side effects=>sfx>.'Found' status
This icon displays whether the
message has been <found> or not.
Clicking the icon will toggle
the status.
This may have <side effects=>sfx>.'Read' lock
This icon shows whether or not the
<read> attribute is kept fixed in
the current <group>.
Clicking this icon will toggle it,
thus changing the group you are
reading. Click for an <example=>lockeg>.Lock usage
An example on how the locks are used:

If you are reading a new message, and
you toggle the new-lock ON, you will
hereafter ONLY be reading new messages.'Sent' lock
This icon shows whether or not the
<sent> attribute is kept fixed in
the current <group>.
Clicking this icon will toggle it,
thus changing the group you are
reading. Click for an <example=>lockeg>.'New' lock
This icon shows whether or not the
<new> attribute is kept fixed in
the current <group>.
Clicking this icon will toggle it,
thus changing the group you are
reading. Click for an <example=>lockeg>.'Personal' lock
This icon shows whether or not the
<personal> attribute is kept fixed
in the current <group>.
Clicking this icon will toggle it,
thus changing the group you are
reading. Click for an <example=>lockeg>.'Marked' lock
This icon shows whether or not the
<marked> attribute is kept fixed
in the current <group>.
Clicking this icon will toggle it,
thus changing the group you are
reading. Click for an <example=>lockeg>.'Crash' lock
This icon shows whether or not the
<crashmail> attribute is kept fixed
in the current <group>.
Clicking this icon will toggle it,
thus changing the group you are
reading. Click for an <example=>lockeg>.'Found' lock
This icon shows whether or not the
<found> attribute is kept fixed in
the current <group>.
Clicking this icon will toggle it,
thus changing the group you are
reading. Click for an <example=>lockeg>.Incoming window
This is the incoming window.